Overview

The SlaveStart control executes a slave application. It is used in a master application as part of Modularity. The control begins by locating the slave application whose name equals the SlaveName property. If the slave is found then a TCP/IP connection is established and the call is passed to the slave. The slave executes until either a disconnect occurs or a SlaveEnd control is encountered. While the slave is executing, all telephony, TTS, and ASR actions are sent back to the SlaveStart control, which executes them on behalf of the slave. When the slave is finished, the call is passed back to the master and the SlaveStart control exits the Done or Disconnect exitnode.

The SlaveStart exits the Error control if the slave cannot be located or if a communication error occurs while processing the call in the slave.